Blog

Luis Majano

October 15, 2008

Spread the word


Share your thoughts

I have had some suggestions for the fwreinit flag to be protected in order to reinitialize the application at hand. What do you think? Is this overkill? The application reinitializes, but it does not crash. It just adds some extra cycles to the request in order to clear and reinit the app. Please send me your comments, suggestions? Should an application reinit, be password protected? Thanks, Luis

Add Your Comment

(3)

Dec 06, 2006 03:53:29 UTC

by Sana

Hi Luis,

I think it really important to keep our APP more secure. Why we allow site users to reinit our app. some users they just play with these kind of things and keep reinit app. In my app i am using onAppinit method to call global components + static data queriries and other global static info. so keep reinit the app cause some problem of server timeout and also whole system get very slow.

Thanks Sana

Dec 06, 2006 08:38:38 UTC

by Rob Gonda

If you allow to set a init key and init password is enough. You can set it to a complex password which no user could guess. That's secure enough for me. p.s. this captcha text is really annoying. Check out Charlie's solution, also default in a latest version of blogCFC

Dec 06, 2006 15:26:06 UTC

by Luis Majano

Thanks Rob!! You are the details man!! jeje.

Will take a look at it.

Recent Entries

Introducing bx-jwt: Enterprise-Grade JSON Web Tokens for BoxLang 🔐

Introducing bx-jwt: Enterprise-Grade JSON Web Tokens for BoxLang 🔐

JWT authentication is everywhere. But rolling it correctly — with proper algorithm enforcement, key management, clock skew handling, JWE encryption, and zero security footguns — is anything but trivial. Today, we're shipping bx-jwt, a production-ready JWT/JWE module for BoxLang that handles all of it out of the box, so you can focus on building, not fighting cryptography.

Luis Majano
Luis Majano
May 22, 2026
What “Modernize or Die” Really Means in 2026

What “Modernize or Die” Really Means in 2026

“Modernize or Die” is not about forcing teams into MVC, chasing trends, or rewriting every CFML application from scratch. It means making sure your applications, teams, and processes can survive the future: easier to maintain, test, secure, deploy, document, hire for, and evolve. In 2026, modernization is less about adopting the newest pattern and more about reducing business risk, protecting the value already built into your systems, and ensuring CFML applications remain credible, sustai...

Cristobal Escobar
Cristobal Escobar
May 22, 2026